Mobile application configurations to enable data transfers

ABSTRACT

Various systems, mediums, and methods may involve a provider application configured to access a user account associated with a provider server. For example, a system may perform operations to identify one or more other applications installed on the mobile device that may be configured to communicate with the provider server. The system may determine data required by the other applications to perform one or more data transfers with the user account. The system may cause the provider application to send the data required to the other applications. As such, the other applications may be enabled to perform one or more data transfers with the user account based on the data sent to the other applications.

BACKGROUND

A number of mobile applications may be installed on a mobile computingdevice. For example, consider a scenario where a user of a mobile devicesearches for a given application to install the application on themobile device. Further, the user may select the application possiblyfrom a number of other applications available from the search results.Based on a selection of the application, the mobile device may begininstalling the application. Yet, possibly based on the particularapplication being installed, the application may require various formsof information from the user, such as credential information. Inparticular, the application may require the user's email address,username, password, phone number, home address, and/or other types ofinformation to operate the application.

As demonstrated in the scenario above, there may be a number of stepssimply to install a single application and operate the application.Thus, there may be various inconveniences and/or inefficiencies inpractice associated with installing the application and operating theapplication. In addition, these inconveniences and/or inefficiencies maybe proportionally increased based on the number of applications that theuser may wish to install and/or operate. As provided above, there ismuch need for technological advancements in various aspects of computertechnology in the realm of computer networks and particularly withmobile applications configured to more efficiently perform datatransfers.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary system, according to anembodiment;

FIG. 2A illustrates an exemplary system with a provider application,according to an embodiment;

FIG. 2B illustrates an exemplary system with a provider applicationconfigured to transfer data, according to an embodiment;

FIG. 2C illustrates the exemplary system with a provider applicationincluding the applications, according to an embodiment;

FIG. 2D illustrates the exemplary system with a given application,according to an embodiment;

FIG. 3A illustrates an exemplary system with a number of installableapplications, according to an embodiment;

FIG. 3B illustrates an exemplary mobile system, according to anembodiment;

FIG. 4A illustrates an exemplary process chart, according to anembodiment;

FIG. 4B illustrates an exemplary process chart with additional steps,according to an embodiment;

FIG. 5A illustrates an exemplary process chart, according to anembodiment;

FIG. 5B illustrates an exemplary process chart with additional steps,according to an embodiment; and

FIG. 6 illustrates an exemplary method, according to an embodiment.

Embodiments of the present disclosure and their advantages may beunderstood by referring to the detailed description herein. It should beappreciated that reference numerals may be used to illustrate variouselements and features provided in the figures. The figures mayillustrate various examples for purposes of illustration and explanationrelated to the embodiments of the present disclosure and not forpurposes of any limitation.

DETAILED DESCRIPTION

As described above, there may be various inconveniences and/orinefficiencies in practice associated with installing mobileapplications and operating the applications. For example, consider thescenarios described above, a user may be required to enter informationfor each application installed, such as an email address, a username,and/or a password, among other forms of credential information. Thus,having to enter such information for a number of applications downloadedmay further accumulate such inconveniences.

In some embodiments, an application described herein may be a mobileapplication configured to alleviate the various inconveniences and/orinefficiencies described above and further herein. In some instances,the application may be configured to perform a number of data transfersfor a user account with a given provider, such as PayPal, Inc. of SanJose, Calif., USA. For example, the application, possibly referred to asa provider app, a mobile provider app, and/or a provider application,may be configured to perform a fund transfer with the user accountassociated with the provider. Yet further, the provider application maybe configured to identify one or more other applications on the mobiledevice configured to perform a fund transfer with the user accountassociated with the provider. In practice, the provider application maysend a message and/or a notification to the other applications thatindicates the user is authorizing the other applications to access theuser account with the provider as a primary funding source for the otherapplications.

In some embodiments, the provider application may also be configured toidentify data required by the other applications such that the otherapplications may be enabled to perform fund transfers with the useraccount with the provider. For example, referring to the scenariosabove, the provider application may identify whether the otherapplications require the user's credential information, such as theuser's email address, username, password, phone number, home address,and/or other types of information, such that the other applications maybe installed on the mobile device. Further, the provider application mayidentify whether the other applications require such credentialinformation to perform data transfers, e.g., fund transfers, with theuser account associated with the provider. Further, the providerapplication may enable the other applications to perform data transferswith the user account. In some instances, the provider application maysend, e.g., read and/or write, the data required to the otherapplications. Notably, the provider application may send various formsof data to each of the other applications, as each of the otherapplications may require different forms of data to perform the datatransfers with the user account associated with the provider. As aresult, when the user accesses and/or uses one of the otherapplications, no additional authentication input (such as entry of apassword) is required from the user.

In some embodiments, the provider application may be activated with theother applications. For example, the provider application may beactivated in response to a user input to the mobile device. As such, theother applications may be enabled to perform the data transfers, e.g.,fund transfers, with the user account associated with the provider. Insome instances, the provider application may display a respective iconfor each of the other applications on a graphical user interface of themobile device. Further, the provider application may display arespective enable button for each of the other applications. As such,the provider application may be configured to enable the otherapplications to perform the data transfers with the user accountassociated with the provider, possibly based on user inputs receivedwith the respective enable buttons. Yet further, the providerapplication may display respective toggle buttons for each of the otherapplications on the graphical user interface. As such, the providerapplication may be configured to enable the other applications toperform the data transfers or disable the other application fromperforming the data transfers, possibly based on user inputs receivedwith the respective toggle buttons.

In practice, consider a scenario where the other applications mayinclude a food application, a hotel application, a rental application,and/or a taxi application, among other types of applications. As such,the provider application may enable these other applications to accessthe user account with the provider, particularly enabling the otherapplications to perform data transfers, e.g., fund transfers, with theuser account. For example, the food application may be enabled togenerate food orders with funds from the user account, the hotelapplication may enabled to generate hotel reservations with funds fromthe user account, the rental application may be enabled to generaterental reservations with funds from the user account, and the taxiapplication may be enabled to generate taxi reservations with fund fromthe user account, among other possibilities with additional applicationsas well, where the payment is automatically defaulted to the paymentprovider and/or the user does not need to separately authenticatethrough those applications.

FIG. 1 is a simplified block diagram of an exemplary system 100,according to an embodiment. As shown, the system 100 may include aserver 102. The server 102 may be configured to perform operations of aprovider, such as PayPal, Inc. of San Jose, Calif., USA. Further, thesystem 100 may also include client device 104 and the client device 106.As such, the server 102 and the client devices 104 and 106 may beconfigured to communicate over the one or more communication networks108. As shown, the system 100 includes multiple computing devices 102,104, and/or 106.

The system 100 may operate with more or less than the computing devices102, 104, and/or 106 shown in FIG. 1, where each device may beconfigured to communicate over the one or more communication networks108, possibly to transfer data accordingly. The one or morecommunication networks 108 may include a packet-switched networkconfigured to provide digital networking communications and/or exchangedata of various forms, content, type, and/or structure. In someinstances, the one or more communication networks 108 may include a datanetwork, a private network, a local area network, a wide area network, atelecommunications network, and/or a cellular network, among otherpossible networks. In some instances, the communication network 108 mayinclude network nodes, web servers, switches, routers, base stations,microcells, and/or various buffers/queues to transfer data/data packets122 and/or 124.

The data/data packets 122 and/or 124 may include the various forms ofdata associated with the user accounts described herein. The data/datapackets 122 and/or 124 may be transferrable using communicationprotocols such as packet layer protocols, packet ensemble layerprotocols, and/or network layer protocols, among other types ofcommunication protocols. For example, the data/data packets 122 and/or124 may be transferrable using transmission control protocols and/orinternet protocols (TCP/IP). In various embodiments, each of thedata/data packets 122 and 124 may be assembled or disassembled intolarger or smaller packets of varying capacities, such as capacitiesvarying from 1,000 to 1,100 bytes, for example, among other possibledata capacities. As such, data/data packets 122 and/or 124 may betransferrable over the one or more networks 108 and to various locationsin the one or more networks 108.

In some embodiments, the server 102 may take a variety of forms. Theserver 102 may be an enterprise server, possibly operable with one ormore operating systems to facilitate the scalability of the architecturewithin the system 100. For example, the server 102 may operate with aUnix-based operating system configured to integrate with a growingnumber of other servers in the one or more networks 108, the clientdevices 104 and/or 106, among other computing devices configured tocommunicate with the system 100. The server 102 may further facilitateworkloads associated with numerous data transfers in view of anincreasing number of applications on the client devices 104 and/or 106.In particular, the server 102 may facilitate the scalability relative tosuch increasing number of data transfers to eliminate data congestion,bottlenecks, and/or transfer delays.

In some embodiments, the server 102 may include multiple components,such as one or more hardware processors 112, non-transitory memories114, non-transitory data storages 116, and/or communication interfaces118, among other possible components described in relation to FIG. 1,any of which may be communicatively linked via a system bus, network, orother connection mechanism 122. The one or more hardware processors 112may take the form of a multi-purpose processor, a microprocessor, aspecial purpose processor, a digital signal processor (DSP) and/or othertypes of processing components. For example, the one or more hardwareprocessors 112 may include an application specific integrated circuit(ASIC), a programmable system-on-chip (SOC), and/or a field-programmablegate array (FPGA). In particular, the one or more hardware processors112 may include a variable-bit (e.g., 64-bit) processor architectureconfigured to transfer the data packets 122 and/or 124. As such, the oneor more hardware processors 112 may execute varying instructions sets(e.g., simplified and complex instructions sets) with fewer cycles perinstruction than other general-purpose hardware processors, therebyimproving the performance of the server 102.

In practice, for example, the one or more hardware processors 112 may beconfigured to read instructions from the non-transitory memory component114 to cause the system 100 to perform operations. For example, thesystem 100 may cause a provider application on the client device 104 toidentify one or more other applications on the client device 104configured to communicate with the provider server 102. The system 100may determine data required by the other applications such that theother applications may perform data transfers with the user account.Further, the system 100 may also cause the provider application to sendthe data required to the other applications. Yet further, the system 100may also enable the one or more other applications to perform the one ormore data transfers based on the data required sent to the one or moreother applications.

The non-transitory memory component 114 and/or the non-transitory datastorage 116 may include one or more volatile, non-volatile, and/orreplaceable storage components, such as magnetic, optical, and/or flashstorage that may be integrated in whole or in part with the one or morehardware processors 112. Further, the memory component 114 may includeor take the form of a non-transitory computer-readable storage medium,having stored thereon computer-readable instructions that, when executedby the hardware processing component 112, cause the server 102 toperform operations described in this disclosure, illustrated by theaccompanying figures, and/or otherwise contemplated herein.

The communication interface component 118 may take a variety of formsand may be configured to allow the server 102 to communicate with one ormore devices, such as the client devices 104 and/or 106. For example,the communication interface 118 may include a transceiver that enablesthe server 102 to communicate with the client devices 104 and/or 106over the one or more communication networks 108. In some instances, thecommunication interface 118 may include a wired interface, such as anEthernet interface, to communicate with the client devices 104 and/or106. Further, in some instances, the communication interface 118 mayinclude a cellular interface, such as a Global System for MobileCommunications (GSM) interface, a Code Division Multiple Access (CDMA)interface, and/or a Time Division Multiple Access (TDMA) interface. Yetfurther, in some instances, the communication interface 118 may includea wireless local area network interface such as a WI-FI interfaceconfigured to communicate with a number of different protocols. As such,the communication interface 118 may include a wireless interfaceoperable to transfer data over short distances utilizingshort-wavelength radio waves in approximately the 2.4 to 2.485 GHzrange. In some instances, the communication interface 118 maysend/receive data or data packets 122 and/or 124 to/from client devices104 and/or 106.

The client devices 104 and 106 may also be configured to perform avariety of operations such as those described in this disclosure,illustrated by the accompanying figures, and/or otherwise contemplatedherein. In particular, the client devices 104 and 106 may be configuredto transfer data packets 122 and/or 124 associated with a user accountto and from the server 102. The data packets 122 and/or 124 may alsoinclude location data such as Global Positioning System (GPS) data orGPS coordinate data, triangulation data, beacon data, WI-FI data, sensordata, movement data, and/or temperature data, among other types of data.

In some embodiments, the client devices 104 and 106 may include or takethe form of a smartphone system, a personal computer (PC) such as alaptop device, a tablet computer device, a wearable computer device, ahead-mountable display (HMD) device, a smart watch device, and/or othertypes of computing devices configured to transfer data associated with auser account. The client devices 104 and 106 may include variouscomponents, including, for example, input/output (I/O) interfaces 130and 140, communication interfaces 132 and 142, hardware processors 134and 144, and non-transitory data storages 136 and 146, respectively, allof which may be communicatively linked with each other via a system bus,network, or other connection mechanisms 138 and 148, respectively.

The I/O interfaces 130 and 140 may be configured to receive inputs fromand provide outputs to users of the client devices 104 and 106. Forexample, the I/O interface 130 may include a graphical user interface(GUI) configured to receive a user input that activates the providerapplication with the other applications. Thus, the I/O interfaces 130and 140 may include displays and/or input hardware with tangiblesurfaces such as touchscreens with touch sensors and/or proximitysensors configured with variable sensitivities to detect the user touchinputs. The I/O interfaces 130 and 140 may also be synched with amicrophone, sound speakers, and/or other audio mechanisms configured toreceive voice commands. Further, the I/O interfaces 130 and 140 may alsoinclude a computer mouse, a keyboard, and/or other interface mechanisms.In addition, I/O interfaces 130 and 140 may include output hardware,such as one or more touchscreen displays, haptic feedback systems,and/or other hardware components.

In some embodiments, communication interfaces 132 and 142 may take avariety of forms. For example, communication interfaces 132 and 142 maybe configured to allow client devices 104 and 106, respectively, tocommunicate with one or more devices according to a number of protocolsdescribed or contemplated herein. For instance, communication interfaces132 and 142 may be configured to allow client devices 104 and 106,respectively, to communicate with the server 102 via the one or morecommunication networks 108. The processors 134 and 144 may include oneor more multi-purpose processors, microprocessors, special purposeprocessors, digital signal processors (DSP), application specificintegrated circuits (ASIC), programmable system-on-chips (SOC),field-programmable gate arrays (FPGA), and/or other types of processingcomponents described or contemplated herein.

The data storages 136 and 146 may include one or more volatile,non-volatile, removable, and/or non-removable storage components, andmay be integrated in whole or in part with processors 134 and 144,respectively. Further, data storages 136 and 146 may include or take theform of non-transitory computer-readable mediums, having stored thereoninstructions that, when executed by processors 134 and 144, cause theclient devices 104 and 106 to perform operations, respectively, such asthose described in this disclosure, illustrated by the accompanyingfigures, and/or otherwise contemplated herein.

In some embodiments, the client device 104 may include a providerapplication that enables other applications of the client device 104 toperform data and/or fund transfers with the user account. For example,the data and/or fund transfers may be encoded in the data packet 122 toestablish a connection with the server 102. As such, the data packet 122may initiate a search of an internet protocol (IP) address of the server102 that may take the form of the IP address, “192.168.1.102,” forexample. In some instances, an intermediate server, e.g., a domain nameserver (DNS) and/or a web server, possibly in the one or more networks108 may identify the IP address of the server 102 to establish theconnection between the client device 104 and the server 102. As such,the server 102 may complete the transfer, possibly based on the datapacket 122.

It can be appreciated that the server 102 and the client devices 104and/or 106 may be deployed in various other ways. For example, theoperations performed by the server 102 and/or the client devices 104 and106 may be performed by a greater or a fewer number of devices. Further,the operations performed by two or more of the devices 102, 104, and/or106 may be combined and performed by a single device. Yet further, theoperations performed by a single device may be separated or distributedamong the server 102 and the client devices 104 and/or 106. In addition,the client devices 104 and/or 106 may be operated and/or maintained bydifferent users such that each client device 104 and/or 106 may beassociated with one or more respective user accounts.

Notably, a user account associated with a provider may be displayed onthe client device 104, possibly with the I/O interface 130. For example,a provider application of the client device 104 may be configured toaccess the user account displayed on the I/O interface 130. In someinstances, the user account may be a personal account with funds.Further, the user account may be a corporate account, such thatemployees, staff, worker personnel, and/or contractors, among otherindividuals may have access to the corporate account. Further, anaccount may be a family account created for multiple family members,where each member may have access to the account. Yet further, it shouldbe noted that a user may be a number of individuals, a group, and/orpossibly a robot, a robotic device, and/or a robotic system, among othercomputing devices capable of transferring data associated with the useraccount. In some instances, data may be required to access the useraccount and/or perform a transfer with the account. For example, thedata required may include credential information, such as a login, anemail address, a username, a password, a phone number, a security code,an encryption key, authentication data, biometric data (e.g.,fingerprint data), and/or other types of data to access the user accountand/or perform a transfer with the account.

FIG. 2A illustrates an exemplary system 200 with a provider application202, according to an embodiment. As shown, the provider application 202may be displayed on a computing device, such as the client device 104described above in relation to FIG. 1, possibly with the I/O interface130. The provider application 202 may be configured to access a useraccount with a provider, such as PayPal, Inc. of San Jose, Calif., USA.

Further, as illustrated, the provider application 202 may include aninput location 204 that indicates, “Activate Provider App 202 with OtherApps 214-224.” As such, by selecting the input location 204, theprovider application 202 may identify the other applications 214-224configured to communicate and/or perform data transfers with a providerserver, such as the provider server 102. The other applications 214-224may be determined by the provider, such as by determining whichentities, merchant entities, and/or merchants associated with thoseother applications 214-224 are configured and/or authorized to receivefunds from the provider. For example, the other applications 214-224 maybe determined with a search of a database or memory storing suchinformation, such as the data storage 116 of the provider server 102. Asnoted, the data transfers with the provider server 102 described abovemay include a fund transfer from the user account maintained by theprovider server 102. As such, the applications 214-224 may be identifiedbased on the applications 214-224 being configured to perform the fundtransfer with the user account with the provider. In particular, theapplications 214-224 may be associated with respective entities,merchant entities, and/or merchants that accept fund transfers from useraccounts with the provider. Notably, the applications 214-224 mayinclude a subset of all the applications installed and/or downloaded bythe mobile system 200.

In addition, by selecting the input location 206 that indicates, “NotNow,” the provider application 202 may decline the option to activatethe provider application 202 with the other applications 214-222.Further, by selecting the input location 208 that indicates, “SetOptions,” the provider application 202 may provide an option menu thatmay provide various options with the provider application 202 requestingthe user to activate the provider application 202 with the otherapplications 214-224. Yet further, by selecting the input location 210that indicates, “Skip,” the provider application 202 may jump and/orskip forward to a transfer menu to provide various options to make datatransfers without activating the provider application 202 with the otherapplications 214-224.

In some embodiments, the data 212 required by the other applications214-224 may be determined. For example, by selecting the input location204, the data 212 required by the other applications 214-224 may bedetermined such that the applications 214-224 may perform one or moredata transfers with the user account. In some instances, the providerapplication 212 may send the data required 212 to the other applications214-224. In such instances, the applications 214-224 may be enabled toperform the one or more data transfers with the user account associatedwith the provider and/or the provider server 102.

In some embodiments, the data required 212 by the one or more otherapplications 214-224 to perform the one or more data transfers mayinclude various types of data associated with the user accountassociated with the provider and/or the provider server 102. As such,the system 200 and/or the provider application 202 may determine thedata 212 required by the one or more other applications 214-224 toperform data transfers with the user account includes an email addressand/or a password. Notably, the user account may be accessed with theprovider application 202 based on the email address and/or the passwordentered to and/or received from the provider application 202. Further,the system 200 may cause the provider application 202 to send the emailaddress and/or the password to the one or more other applications214-224. Yet further, the system 200 and/or the provider application 202may enable the one or more other applications 214-224 to perform the oneor more data transfers based on the email address and/or the passwordsent to the one or more other applications 214-224. In otherembodiments, the other applications 214-224 may be authorized to pull orotherwise retrieve specific authorized information, such as from theprovider application 202 or other storage areas associated with theprovider (e.g., the data storage 116 of the provider server 102),possibly for authorizing the one or more other applications 214-224 totransfer funds with the user account for a transaction associated withthe one or more other applications 214-224.

FIG. 2B illustrates the exemplary system 200 with the providerapplication 202 configured to transfer data 234-244, according to anembodiment. The exemplary system 200, possibly referred to as the mobilesystem 200, may include various components and/or aspects of the system100 described above in relation to FIG. 1. As shown, the providerapplication 202 may include the input locations 206, 208, and 210described above in relation to FIG. 2A. As noted above, the providerapplication 202 may identify the other applications 214-224 configuredto communicate with the provider server 102 described above. Asdescribed, the provider application 202 may be activated with the otherapplications 214-224, possibly based on an input received by the mobilesystem 200. For example, by selecting the input location 204, the otherapplications 214-224 may be enabled to perform one or more datatransfers with the user account.

In some embodiments, the data 234-244 may be required by theapplications 214-224 to perform the one or more data transfers with theuser account. Thus, in some instances, the data 234-244 required may bedetermined and/or identified by the mobile system 200. In someinstances, the data 234-244 required may be determined and/or identifiedby the provider application 202. For example, by selecting the inputlocation 204, the mobile system 200 and/or the provider application 202may determine data 234-244 required by the applications 214-224 suchthat the applications 214-224 may be enabled to perform one or more datatransfers with the user account. As shown, the data 234, 236, 238, 240,242, and 244 may be required by the applications 214, 216, 218, 220,222, and 224, respectively.

In some embodiments, the respective data 234, 236, 238, 240, 242, and244 required by the corresponding applications 214, 216, 218, 220, 222,and 224 may be determined to enable each of the applications 214, 216,218, 220, 222, and 224 to perform one or more corresponding datatransfers with the user account and/or using the user account. In someinstances, the data 234-244 may include the same or different forms ofdata, particularly based on the respective applications 214, 216, 218,220, 222, and 224, and/or the respective requirements of each of theapplications 214-224. In such instances, the mobile system 200 may causethe provider application 202 to send the respective data 234, 236, 238,240, 242, and 244 required to each of the one or more other applications214, 216, 218, 220, 222, and 224. Further, each of the one or more otherapplications 214, 216, 218, 220, 222, and 224 may be enabled to performcorresponding data transfers with the user account based on therespective data 234, 236, 238, 240, 242, and 244 sent to each of theother corresponding applications 214, 216, 218, 220, 222, and 224.

For example, the application 214 may require data 234 including an emailaddress and a password to perform data transfers with the user account.The application 216 may require data 236 including a phone number, anemail address, a username, and a password to perform data transfers withthe user account. The application 218 may require data 238 including anemail address, a zip code, and a password to perform data transfers withthe user account. The application 220 may require data 240 including anemail address and a password to perform data transfers with the useraccount. The application 222 may require data 242 including a phonenumber, an email address, username, and a password to perform datatransfers with the user account. The application 224 may require data244 including an email address, a zip code, and a password to performdata transfers with the user account.

FIG. 2C illustrates the exemplary system 200 with the providerapplication 202 including the applications 214-224, according to anembodiment. As shown on the left side of FIG. 2C, an example embodimentof the provider application 202 includes the input locations 204, 206,208, and 210 as described above in relation to FIGS. 2A-2B. Forillustrative purposes, on the right side of FIG. 2C, another exampleembodiment of the provider application 202 includes the otherapplications 214-224 configured to communicate and/or perform datatransfers with the provider. As noted, by selecting the input location204, the provider application 202 may identify the applications 214-224from a number of various other applications of the mobile system 200 anddisplay the applications 214-224, as shown on the right side of FIG. 2C.

As shown, the applications 214, 216, and/or 218 may take the form of afood, drink, and/or a restaurant application, among other types ofmobile applications. The application 220 may take the form of a hotelapplication, the application 222 may take the form of a rentalapplication, and the application 224 may take the form of a taxiapplication. As such, the applications 214, 216, and/or 218 may beenabled to perform a data transfer that generates respective ordersbased on the data required 234, 236, and/or 238 sent to the applications214, 216, and/or 218, respectively.

The hotel application 220 may be enabled to perform a data transfer thatgenerates a hotel reservation based on the required data 240 sent to thehotel application 220. The rental application 222 may be enabled toperform a data transfer that generates a rental reservation based on therequired data 242 sent to the rental application 222. The taxiapplication 224 may be enabled to perform a data transfer that generatesthe taxi reservation based on the required data 244 sent to the taxiapplication 224. The data transfers described above may be performedwith the applications 214-224 and a provider server, such as the server102 described above.

Further, in some instances, the applications 214-224 may be referred toas application icons 214-224. As shown, the provider application 202 maydisplay respective application icons 214-224 for each of the otherapplications on a graphical user interface, such as the I/O interface130 described above in relation to FIG. 1. In some instances, theprovider application 202 may display respective enable buttons 254-264for each of the applications 214-224 on the graphical user interface130. As such, the applications 254-256 may be enabled to perform the oneor more data transfers with the user account, possibly based on inputsreceived with the respective enable buttons 254-264.

By selecting the respective enable buttons 254-264, the applications214-224 may be enabled to transfer funds from the user account with theprovider to the respective entities, merchant entities, and/or merchantsof the applications 214-224. In some instances, by selecting therespective enable buttons 254-264, the provider application 202 maydetermine the data required (e.g., login credentials, email addresses,usernames, and/or passwords) by the corresponding applications 214-224to perform the data transfers with the user account. Further, theprovider application 202 may send the respective data 234-244 to thecorresponding applications 214-224 to enable the applications 214-224 toperform the data transfers with the user account. Notably, in variousinstances, the provider application 202 and the applications 214-224 mayeach be associated with different providers, entities, merchantentities, and/or merchants.

In some embodiments, a number of offers and/or deals may be associatedwith the enable buttons 254-264. For example, by selecting the enablebutton 254, the application 214 may provide a “$10 off meal” offer.Further, by selecting the enable button 256, the application 216 mayprovide a “$20 off dinner” offer. Yet further, by selecting the enablebutton 258, the application 218 may provide a “free meal” offer. Inaddition, by selecting the enable button 260, the application 220 mayprovide a “one night free” offer. Further, by selecting the enablebutton 262, the application 222 may provide a “$30 off rental” offer.Yet further, by selecting the enable button 264, the application 224 mayprovide a “$5 off ride” offer. Notably, such offers may be provided bythe provider of the provider application 202 and/or the entities and/ormerchants of the applications 214-224.

In some embodiments, referring back to FIGS. 2A-2C, the system 200 maydetermine the provider application 202 configured to access a useraccount associated with a provider server (e.g., the provider server102). The mobile system 200 may identify one or more other applications214-224 of the mobile system 200 configured to communicate with theprovider server 102. In some instances, the one or more otherapplications 214-224 may be displayed by the mobile system 200. Themobile system 200 may receive a user selection 261 associated with theone or more other applications 214-224 displayed. In one particularexample, the user selection 261 is associated with the selectedapplication 220. Yet, various other applications 214-218, 222, and/or224 may be selected as well. The mobile system 200 may determine data240 required for the selected application 220 to perform one or moredata transfers with the user account. As such, the mobile system 200 maycause the provider application 202 to send the data 240 required to theselected application 220. The mobile system 200 may enable the selectedapplication 220 to perform the one or more data transfers with the useraccount based on the data 240 sent to the selected application 220.

In some embodiments, referring back to FIG. 2C, the mobile system 200may receive a user indication (e.g., an input to the input location 204)to activate the provider application 202 with the one or more otherapplications 214-224, such as the selected application 220. For example,the selected application 220 may be enabled to perform the one or moredata transfers with the user account based on activating the providerapplication 202 with the selected application 220.

FIG. 2D illustrates the exemplary system 200 with the application 220,according to an embodiment. As noted above, by selecting one or more ofthe enable buttons 254-264 shown in FIG. 2C, the correspondingapplications 214-224 may be enabled to perform data transfers with theuser account described herein. In some instances, the providerapplication 202 may be activated with the respective applications214-224 based on the corresponding enable buttons 254-264 beingselected. As such, the applications 214-224 may be enabled to performfund transfers from the user account accessible by the providerapplication 202 without the user having to enter authenticationcredentials or otherwise authenticate the applications 214-224 and/orthrough the applications 214-224. Thus, funds may be transferred fromthe user account to the entities and/or merchants associated with theapplications 214-224.

In addition, by selecting the one or more enable buttons 254-264,various other operations may be performed. For example, by selecting theenable button 260 shown in FIG. 2C, the hotel application 220 may begenerated by the graphical user interface of the mobile system 200,possibly an interface that takes the form of the I/O interface 130. Asshown, the hotel application 220 may provide a notification 270 thatindicates, “Is user@provider.com your email account for Hotel App 220?”It should be noted that the email address, “user@provider.com,” may bethe email address associated, represented, and/or stored with theprovider application 202 and/or the provider server 102. Thus, variousinput locations 272 and 274 may be selected, possibly to activate theprovider application 202 with the hotel application 220 such that thehotel application 220 may be enabled to make data transfers with theuser account associated and/or maintained with the provider server 102.As shown, the input location 272 indicates “Agree and Continue” and theinput location 274 indicates “Change Email.”

For example, by selecting the input location 272, the hotel application220 may provide the interface 276. As shown, the interface 276 includesa notification 278 that indicates, “Provider App 202 is Activated withHotel App 220,” possibly where the email address, “user@provider.com,”is the email address associated, represented, and/or stored with thehotel application 202. As such, the hotel application 220 may be enabledto make data transfers with the user account of the provider application202 associated and/or maintained with the provider server 102. It shouldbe noted that allowing the user to select the input location 272 mayeliminate the user from having to manually enter an email address forthe hotel application 220, thereby alleviating the inconveniences and/orinefficiencies described above with installing mobile applications.

Further, by selecting the input location 274, one or more other emailsmay be entered with the hotel application 220. As shown, the interface280 includes an input location 282 that indicates, “Enter your loginemail,” possibly where a user may enter their login email for the hotelapplication 220. For example, in a scenario where a user may alreadyhave existing credential information (e.g., an email and a password)with the hotel application 220, the user may enter an existing emailaddress and also activate the provider application 202 with the hotelapplication 220. Notably, by selecting the input location 282, akeyboard may be generated with the hotel application 220, where theexisting email address and/or password may be entered. Further, anotification 284 may indicate, “Provider App 202 will be Activated withHotel App 218,” possibly based on the existing email address and/orpassword entered. As such, the hotel application 220 may be enabled tomake data transfers with the user account of the provider application202 associated and/or maintained with the provider server 102.

FIG. 3A illustrates the exemplary system 300 with a number ofinstallable applications, according to an embodiment. The system 300 mayinclude components and/or aspects of the systems 100 and/or 200described above in relation to FIGS. 1-2D. For example, the provider 302may take the form of the provider application 202 described above. Thehotel application 320 may take the form of the hotel application 220described above. As shown, a notification 306 may indicate, “ProviderApp 302 is Activated with Hotel App 320,” thereby enabling the hotelapplication 220 to make data transfers and/or fund transfers with theuser account of the provider application 302 associated and/ormaintained with the provider server 102.

Further, as shown, the provider application 302 may display a togglebutton 304 that corresponds to the hotel application 320. As such, theprovider application 320 may be enabled to perform data transfers, suchas fund transfers with the user account of the provider application 302described above, possibly based on a user input received with the togglebutton 304. In particular, by moving the toggle button 304 to the rightas shown, the notification 306 may indicate, “Provider App 302 isActivated with Hotel App 320.” As such, the hotel application 220 may beenabled to make data and/or fund transfers with the user account of theprovider application 302. Further, by moving the toggle button 304 tothe left, the notification 306 may indicate, “Provider App 302 isDeactivated from Hotel App 320.” As such, the hotel application 320 maybe disabled from performing data and/or fund transfers with the useraccount of the provider application 302.

As shown, the provider application 302 may also provide a notification308 that indicates, “Discover Other Apps and Services.” Further, theprovider application 302 may provide a number of installableapplications 310, 312, and 314. For example, the application 310 may bea travel application configured to perform data transfers to matchdrivers and passengers, such that the passengers can identify and selectfrom multiple drivers to travel to a given destination. The application312 may be a reservation application configured to perform datatransfers that enable users to make reservations at restaurants andperform fund transfers accordingly to cover their meals. The application314 may be an audiobook application configured to perform data transfersthat operate listening devices, such as the client devices 104 and/or106 described above.

As shown, the provider application 302 may provider a number of installbuttons 330, 332, and 334 that correspond to the installableapplications 310, 312, and/or 314, respectively. Further, the one ormore applications 310, 312, and/or 314 may be installed based on one ormore inputs received with the respective install buttons 330, 332,and/or 334. By selecting one or more of the install buttons 330, 332,and/or 334, the corresponding applications 310, 312, and/or 314 may beinstalled on the mobile system 300. As such, the provider application302 may provide the respective data (e.g., login credentials, emailaddresses, usernames, and/or passwords) to each of the applications 310,312, and/or 314 to install each of the applications 310, 312, and/or314. Further, the applications 310, 312, and/or 314 may be installedsuch that the applications 310, 312, and/or 314 may be configured toperform data and/or fund transfers, with the user account of theprovider application 302. Notably, the applications 310, 312, and/or 314may be installed without requiring the user to create and/or entercredential information for each of the applications 310, 312, and/or314, thereby eliminating the inconveniences and/or the inefficiencies asdescribed herein.

FIG. 3B illustrates the exemplary mobile system 300, according to anembodiment. As shown, the system 300 may take the form of a smartphonewith an input/output (I/O) interface 342. Further, the I/O interface 342may take the form of the I/O interface 130 described above, possiblyreferred to as a graphic display 342 with one or more touch sensorsconfigured to detect touch inputs. Further, the I/O interface 342 maydisplay the provider application 302, the hotel application 320, and theinstallable applications 310, 312, and/or 314, possibly among otherapplications described above in relation to FIGS. 2A-2D. Yet further,the I/O interface 342 may display the toggle button 304, the installbuttons 330, 332, and/or 334, among possibly other buttons describedabove in relation to FIGS. 2A-2D.

Further, the mobile system 300 may include one or more side buttons 346configured to adjust volumes associated with speakers and/or headsetscoupled with the system 300. For example, the side buttons 346 may beconfigured to adjust the volume of the speaker 344, possibly playing oneor more audiobooks associated with the application 314, as describedabove. Yet further, the mobile system 300 may include a button 348 withone or more touch sensors configured receive and/or detect a fingerprintof the user to perform the data and/or fund transfers described herein.As such, the one or more applications 310, 312, 314, and/or 320, amongthe other applications 202 and 214-224 described above, may beconfigured to perform data and/or fund transfers with the user accountassociated with the provider application 302, possibly based on thefingerprint of the user detected and/or received by the mobile system300.

FIG. 4A illustrates an exemplary process chart 400, according to anembodiment. As shown, the process chart 400 includes a providerapplication 402, an input/output (I/O) interface 404, an operatingsystem (OS) 406, and one or more other applications 408. In someinstances, the provider application 402 may take the form of theprovider application 202 and/or the provider application 302 describedabove in relation to FIGS. 1-3B, among other provider applicationsdescribed herein. Further, the I/O interface 404 may take the form ofthe I/O interfaces 130, 140, and/or 342 described above in relation toFIGS. 1-3B, among other I/O interfaces and/or graphical user interfacesdescribed herein. Yet further, the operating system (OS) 406 may be anOS of the server 102, an OS of the client devices 104 and/or 106, an OSof the mobile system 200 and/or 300, among other operating systems ofvarious devices and/or systems described herein. Further, the one ormore other applications 408 may include the one or more otherapplications 214-224, the installable applications 310-314, amongvarious other applications described herein. Thus, the various steps410-416 may be carried out by the server 102 and/or the mobile system200, among other systems and/or devices described herein.

At step 410, the provider application 402 of the mobile device 200 maybe instructed to request an operating system (OS) 406 of the mobiledevice 200 to identify one or more other applications 214-224 of themobile device 200 configured to perform one or more data transfersassociated with the user account described above. For example, theprovider application 402 may send a “Get Apps” call, possibly anapplication programming interface (API) call to the operating system406, to identify the applications 214-224.

At step 412, in response to the request to the operating system (OS) 406of the mobile device 200, application identification data may beretrieved from the operating system 406 that identifies the one or moreother applications 214-224 of the mobile device 200 configured toperform the one or more data transfers associated with the user account.For example, considering the scenario above, based on the Get Apps callsent to the operating system 406, the application identification datamay be retrieved from the operating system 406 to identify theapplications 214-224, possibly from a list of other applications of themobile device 200 as well.

At step 414, in response to retrieving the application identificationdata, the provider application 402 may be instructed to display one ormore application icons 214-224 on an input/output interface 404, e.g., agraphic user interface 404. As noted, the one or more application icons214-224 correspond with the one or more other applications 214-224described herein. As such, referring back to FIG. 2C, the providerapplication 402 may be instructed display the one or more icons 214-224.

At step 416, the provider application 402 may be instructed to send data234-244 to the one or more applications 408 that include theapplications 214-224. The data 234-244 may be required by the one ormore other applications 214-224 to perform the one or more datatransfers associated with the user account. In particular, the one ormore other applications 214-224 may be enabled to perform the one ormore data transfers based on the data 234-244 sent from the providerapplication 402. As noted, the provider application 402 may sendrespective data 234, 236, 238, 240, 242, and/or 244 required by thecorresponding applications 214, 216, 218, 220, 222, and/or 224 to enablethe applications 214-224 to perform the data transfers associated withthe user account.

In some embodiments, the data 234-244 sent to the one or more otherapplications 214-224 may include an email address and/or a passwordassociated with the user account. For example, the provider application402 may provide access to the user account based on the email addressand/or the password. As such, the one or more applications 214-224 maybe enabled to perform the one or more data transfers associated with theuser account based on the email address and/or the password.

In some instances, referring back to FIG. 1, the non-transitory memory114 of the server 102 may include a non-transitory machine-readablemedium having stored thereon machine-readable instructions. Theinstructions may be executed to cause the server 102 to performoperations, such as the steps 410-416 in the process chart 400. Forexample, the server 102 may perform step 410 by causing the providerapplication 404 of the mobile device 200 to request the operating system(OS) 406 of the mobile device 200 to identify the one or more otherapplications 214-244 of the mobile device 200 configured to perform oneor more data transfers associated with the user account.

Further, in response to the request to the operating system (OS) 406,the server 102 may perform step 412 by retrieving applicationidentification data from the operating system 406 that identifies theone or more other applications 214-244 of the mobile device 200configured to perform the one or more data transfers associated with theuser account. In response to retrieving the application identificationdata, the server 102 may perform step 414 by causing the providerapplication 402 to display one or more application icons 214-244 on agraphic user interface 404 that correspond with the one or more otherapplications 214-244. Further, the server 102 may perform the step 416causing the provider application 402 to send the data 234-244 requiredby the one or more other applications 214-224 to perform the one or moredata transfers associated with the user account. In particular, the oneor more other applications 214-224 may be enabled to perform the one ormore data transfers based on the data 234-244 sent from the providerapplication 402.

FIG. 4B illustrates an exemplary process chart 420 with additional steps422 and 424, according to an embodiment. As shown, the process chart 420includes the provider application 402, the I/O interface 404, theoperating system (OS) 406, and/or the one or more applications 408described above in relation to FIG. 4A. Further, the process chart 420includes the steps 410-414 as described above in relation FIG. 4A. Thus,the various steps 410-414, 422, and 424 may be carried out by the server102 and/or the mobile system 200, among other systems and/or devicesdescribed herein.

For example, at step 414, in response to retrieving the applicationidentification data, the provider application 402 may be instructed todisplay one or more application icons 214-224 on an input/outputinterface 404, e.g., a graphic user interface 404. As noted, the one ormore application icons 214-224 may correspond with the one or more otherapplications 214-224 described above. For example, referring back toFIG. 2C, the provider application 402 may be instructed to display theone or more icons 214-224 shown.

In some embodiments, the provider application 402 may be instructed todisplay respective enable buttons 254-264 for each of the correspondingapplications 214-224 on the graphical user interface 404, as describedabove in relation to FIG. 2C. Further, in some instances, the providerapplication 402 may be instructed to display respective toggle buttonsfor each of the corresponding applications 214-224 on the graphical userinterface 404. For example, referring back to FIGS. 3A-B, the togglebutton 304 may be displayed for the corresponding application 320. Yetfurther, in some instances, the provider application 402 may beinstructed to display one or more installable applications 310-314 onthe graphical user interface 404. In addition, the provider application402 may display respective install buttons 330-334 for each of the oneor more installable applications 310-314 on the graphical user interface404.

At step 422, the provider application 402 may receive one or more inputsdetected by the graphical user interface 404. In some instances, theprovider application 402 may receive the one or more inputs from therespective enable buttons 254-264, the respective toggle buttons, suchas the toggle button 304, and/or the respective install buttons 330-334described above.

At step 424, the provider application 402 may be instructed to send data234-244 to the one or more applications 408, possibly including the oneor more other applications 214-224. Further, the data 234-244 may berequired by the one or more other applications 214-224 to perform theone or more data transfers associated with the user account. Inparticular, the one or more other applications 214-224 may be enabled toperform the one or more data transfers based on the data 234-244 sentfrom the provider application 402. As noted, the provider application402 may send respective data 234, 236, 238, 240, 242, and/or 244required by the corresponding applications 214, 216, 218, 220, 222,and/or 224 to enable the applications 214-224 to perform the datatransfers associated with the user account. Notably, the providerapplication 402 may send the data 234-244 required by the one or moreother applications 214-224 based on the one or more inputs received bythe graphical user interface 404 described above in relation to step422.

As noted, referring back to FIG. 1, the non-transitory memory 114 of theserver 102 may include a non-transitory machine-readable medium havingstored thereon machine-readable instructions. The instructions may beexecuted to cause the server 102 to perform operations. For example, theserver 102 may cause the provider application 202 to display respectiveenable buttons 254-264 for each of the one or more other applications214-224 on the graphical user interface 404. Further, the server 102 mayenable the one or more applications 214-224 to perform the one or moredata transfers based on one or more inputs received with the respectiveenable buttons 254-264.

In some embodiments, the server 102 may cause the provider application302 to display respective toggle buttons, such as the toggle button 304described above, for each of the one or more other applications, such asthe application 320. For example, the selected application 320 may beenabled to accept the one or more data transfers based on the userselection 305 received with the respective toggle button 304. Notably,referring back to FIGS. 2A-2D, the one or more other applications214-224, possibly the selected application 220 as shown, may be enabledto perform the one or more data transfers or disabled from performingthe one or more data transfers based on one or more inputs received withthe respective toggle buttons that correspond to the one or more otherapplications 214-224.

In some embodiments, referring to FIG. 3B, the server 102 may cause theprovider application 302 to display one or more installable applications310-314 on the graphical user interface 342. Further, the server 102 maycause the provider application 302 to display respective install buttons330-332 for each of one or more installable applications 310-314 on thegraphic user interface 342. Yet further, the one or more installableapplications 310-314 may be installable based on one or more user inputsreceived with the respective install buttons 330-332 on the graphic userinterface 342.

In some embodiments, the server 102 may cause at least one applicationfrom the one or more installable applications 310-314 to be installedbased on the one or more inputs received with the respective installbuttons 330-334. Further, the server 102 may cause the providerapplication 302 to transfer an email address and/or a password to theinstalled application 310, 312, and/or 314 to enable the installedapplication 310, 312, and/or 314 to perform the one or more datatransfers associated with the user account.

FIG. 5A illustrates an exemplary process chart 500, according to anembodiment. As shown, the process chart 500 includes a providerapplication 502, an input/output (I/O) interface 504, an operatingsystem (OS) 506, one or more networks 508, and one or more otherapplications 510. In some instances, the provider application 502 maytake the form of the provider application 202, 302, and/or 402, amongother applications described above in relation to FIGS. 1-4B. Further,the I/O interface 504 may take the form of the I/O interfaces 130, 140,342, and/or 404, among other interfaces described above in relation toFIGS. 1-4B. Yet further, the operating system 506 may take the form ofthe operating system 406, possibly associated with the server 102, theclient devices 104 and/or 106, the mobile system 200 and/or 300, amongother devices and/or systems described herein.

In addition, the one or more networks 508 may take the form of the oneor more networks 108 described above in relation to FIG. 1, among othernetworks described herein. For example, the one or more networks 508,possibly referred to as one or more provider networks 508, may becontrolled, maintained, and/or owned by the provider of the server 102.In some instances, the one or more networks 508 may include anadvertisement network, a social network, and/or an instant messagingnetwork configured to identify the one or more applications 510, thatmay take the form of the applications 214-224 on the mobile system 200.In such instances, the process 500 may include the mobile system 200generating an advertisement including an incentive based on a purchasemade with the applications 214-224 and displaying the advertisement. Forexample, the mobile device 200 may communicate with the one or morenetworks 508 to generate the notification, “Activate Provider App 202with Apps 214-224,” and display icons that correspond to theapplications 214-224, possibly also with the offers, “$10 off meal,”“$20 off dinner,” “free meal,” “one night free,” “$30 off rental,”and/or “$5 off ride,” among the other offers described herein. Ascontemplated herein, the various steps 512-522 may be carried out by theserver 102 and/or the mobile system 200, among other systems and/ordevices described herein.

At step 512, the provider application 502 of the mobile device 200 maybe instructed to identify one or more other applications 214-224 of themobile device 200 configured to communicate with a provider of theprovider application 502. For example, the provider of the providerapplication 502 may take the form of the provider of the server 102described above in relation to FIG. 1. As such, the provider application502 may send a “Get Apps” call, possibly an application programminginterface (API) call, to the operating system 506 to identify theapplications 214-224.

At step 514, in response to the Get Apps call, the provider application502 may retrieve application identification data from the operatingsystem 506 that identifies the one or more applications 214-224configured to communicate with the provider described above. In someembodiments, the application identification data described aboveindicates one or more installable applications 310-314 configured toperform the one or more data transfers with the provider. In suchinstances, referring back to FIG. 3B, the provider application 502 maytake the form of the provider application 302. As such, the providerapplication 302 may display respective install buttons 330-334 for eachof the one or more installable applications 310-314 on the graphicaluser interface 342 of the mobile device 300. As such, the one or moreinstallable applications 310-314 may be configured to be installed basedon one or more inputs received with the respective install buttons330-334.

In some embodiments, the process 500 may include installing at least oneapplication from the one or more installable applications 310-314 basedon the one or more inputs received with the respective install buttons330-334. Further, the process 500 may include causing the one or morenetworks 508 to send an email address and/or a password to the installedapplication 310-314 to enable the installed application 310-314 toperform the one or more data transfers with the user account.

At step 516, the provider application 502 may be instructed tocommunicate with the one or more networks 508 to retrieve network dataassociated with the one or more applications 214-224. As such, theprovider application 502 may send a “Get Network Data” call, possibly anapplication programming interface (API) call, to the one or morenetworks 508 to retrieve the network data associated with the one ormore applications 214-224.

At step 518, the provider application 502 may retrieve the network dataassociated with the one or more applications 214-224. Based on thenetwork data retrieved, the provider application 502 may determine thedata 234-244 required by the one or more applications 214-224 to performone or more data transfers with a user account associated with theprovider.

At step 520, the provider application 502 may be instructed to send thedata 234-244 required to the one or more networks 508 to enable the oneor more applications 214-224 to perform the one or more data transferswith the user account.

At step 522, the one or more networks 508 may send the data 234-244 tothe one or more applications 510, possibly including the one or moreapplications 214-224. In some instances, the process 500 may includecausing the one or more applications 214-224 to perform a fund transferwith the user account based on the data 234-244 sent to the one or morenetworks 508.

In some embodiments, the data 234-244 sent to the one or more networks508 causes the one or more networks 508 to send an email address and/ora password to the one or more applications 214-224. Further, the one ormore applications 214-224 may be enabled to perform one or more datatransfers with the user account based on the email address and/or thepassword sent to the one or more applications 214-224.

FIG. 5B illustrates an exemplary process chart 530 with additional steps532, 534, and 536, according to an embodiment. As shown, the processchart 530 includes the provider application 502, the I/O interface 504,the operating system (OS) 506, the one or more networks 508, and/or theone or more applications 510 described above in relation to FIG. 5A.Further, the process chart 530 includes the steps 512-518 as describedabove in relation FIG. 5A. Thus, the various steps 512-518 and 532-536may be carried out by the server 102 and/or the mobile system 200, amongother systems and/or devices described herein.

As noted above, the provider application 502 may take the form of theprovider application 202. As such, the provider application 502 mayretrieve the network data associated with the one or more applications214-224. Based on the network data retrieved, the provider application502 may determine the data 234-244 required by the one or moreapplications 214-224 to perform one or more data transfers with a useraccount associated with the provider.

At step 518, the one or more icons may be displayed on the I/O interface504, e.g., the graphical user interface 504, that correspond with theone or more other applications 214-224. For example, referring back toFIG. 2C, the provider application 402 may be instructed display the oneor more icons shown that correspond to the one or more other application214-224.

In some embodiments, the provider application 502 may be instructed todisplay respective enable buttons 254-264 for each of the correspondingapplications 214-224 on the graphical user interface 504, as describedabove in relation to FIGS. 2C. Further, in some instances, the providerapplication 502 may be instructed to display respective toggle buttons,such as the toggle button 304, for each of the correspondingapplications 214-224 on the graphical user interface 504, as describedabove in relation to FIGS. 3A-B. Yet further, in some instances, theprovider application 502 may be instructed to display one or moreinstallable applications 310-314 on the graphical user interface 504.

At step 532, the provider application 502 may receive one or more inputsdetected by the graphical user interface 504. In some instances, theprovider application 502 may receive the one or more inputs from therespective enable buttons 254-264, the respective toggle buttons, suchas the toggle button 304, and/or the respective install buttons 330-334described above.

At step 534, the provider application 402 may be instructed to send thedata 234-244 required to the one or more networks 508 to enable the oneor more applications 214-224 to perform the one or more data transferswith the user account.

At step 536, the one or more networks 508 may send the data 234-244 tothe one or more applications 510, including the one or more applications214-224.

FIG. 6 illustrates an exemplary method 600, according to an embodiment.Notably, one or more steps of the method 600 described herein may beomitted, performed in a different sequence, and/or combined with othermethods for various types of applications contemplated herein.

At step 602, the method 600 may include identifying one or moreapplications of a mobile device configured to communicate with aprovider, where the one or more applications is identified based onapplication identification data retrieved from an operating system ofthe mobile device. For example, the method 600 may include identifyingone or more applications 214-224 of the mobile device 200 configured tocommunicate with one or more of the providers described herein. Further,the one or more applications 214-224 may be identified based onapplication identification data retrieved from an operating system ofthe mobile device 200.

At step 604, in response to identifying the one or more applications,the method 600 may include communicating with one or more networks toretrieve network data associated with the one or more applications. Forexample, in response to identifying the one or more applications214-224, the method 600 may include communicating with one or morenetworks to retrieve network data associated with the one or moreapplications 214-224. In particular, the method 600 may includecommunicating with the one or more networks 108 and/or 508 describedherein to retrieve the network data.

At step 606, based at least on the network data retrieved, the method600 may include determining data required by the one or moreapplications to perform one or more data transfers with a user accountassociated with the provider. For example, the method 600 may includedetermining data 234-244 required by the one or more applications214-224 to perform one or more data transfers with a user accountassociated with the provider.

At step 608, the method 600 may include sending the data required to theone or more networks to enable the one or more applications to performthe one or more data transfers with the user account. For example, themethod 600 may include sending the data 234-244 required to the one ormore networks to enable the one or more applications 214-224 to performthe one or more data transfers with the user account. As noted, themethod 600 may include sending the data 324-244 required to the one ormore networks 108 and/or 508 described herein to perform the one or moredata transfers with the user account, e.g., the fund transfers with theuser account.

The present disclosure, the accompanying figures, and the claims are notintended to limit the present disclosure to the precise forms orparticular fields of use disclosed. As such, it is contemplated thatvarious alternate embodiments and/or modifications to the presentdisclosure, whether explicitly described or implied herein, are possiblein light of the disclosure. Having thus described embodiments of thepresent disclosure, persons of ordinary skill in the art will recognizethat changes may be made in form and detail without departing from thescope of the present disclosure.

1. A mobile system, comprising: a non-transitory memory; and one or morehardware processors coupled to the non-transitory memory and configuredto read instructions from the non-transitory memory to cause the systemto perform operations comprising: determining a provider applicationconfigured to access a user account associated with a provider server;identifying a plurality of other applications of the mobile systemconfigured to communicate with the provider server, wherein identifiersassociated with the plurality of other applications are displayed by themobile system; receiving a user selection of a first application and asecond application from the plurality of other applications displayed;determining, through the provider application and without manual input,a first set of data types required for the first selected application toperform one or more data transfers with the user account and a secondset of data types required for the second selected application toperform the one or more data transfers with the user account, whereinthe first set of data types is different from the second set of datatypes; causing the provider application to send data corresponding tothe first set of data types to the first selected application and datacorresponding to the second set of data to types to the second selectedapplication; and enabling the first and second selected applications toperform the one or more data transfers with the user account based atleast on the data sent to the first and second selected applications. 2.The mobile system of claim 1, wherein the one or more data transfersfrom the user account comprises a fund transfer from the user account,and wherein identifying the plurality of other applications comprises:retrieving, from an operating system of the mobile system identifiers ofa set of applications installed in the mobile system; and identifying asubset of applications within the set of applications that areconfigured to perform the fund transfer with the user account.
 3. Themobile system of claim 1, wherein the operations further comprise:receiving a user indication to activate the provider application withthe first and second selected applications, wherein the first and secondselected applications are enabled to perform the one or more datatransfers with the user account based at least on activating theprovider application with the first and second selected applications. 4.The mobile system of claim 1, wherein the operations further comprise:causing the provider application to display a respective icon for eachof the one plurality of other applications on a graphical user interfaceof the mobile system; and causing the provider application to display arespective enable button for each of the plurality of other applicationson the graphical user interface, wherein the first and second selectedapplications are enabled to perform the one or more data transfers withthe user account based at least on the user selection received with therespective enable buttons.
 5. The mobile system of claim 1, wherein theoperations further comprise: causing the provider application to displaya respective toggle button for each of the plurality of otherapplications on a graphical user interface of the mobile system, whereinthe first and second selected applications is enabled to accept the oneor more data transfers based at least on the user selection receivedwith the respective toggle buttons.
 6. The mobile system of claim 1,wherein the first set of data types comprises an email address data anda password data type, wherein causing the provider application to sendthe data required corresponding to the first set of data types comprisescausing the provider application to send an email address and a passwordassociated with the user account to the first selected application, andwherein enabling the first selected application to perform the one ormore data transfers comprises enabling the first selected application toperform the one or more data transfers based at least on the emailaddress the password sent to the first selected application.
 7. Themobile system of claim 1, wherein determining the first set of datatypes and the second set of data types required for the first and secondselected applications, respectively, comprises retrieving, via anetwork, network data associated with the first and second selectedapplications, respectively, wherein the first set of data types isdetermined based on the retrieved network data corresponding to thefirst selected application and the second set of data types isdetermined based on the retrieved network data corresponding to thesecond selected application.
 8. The mobile system of claim 1, whereinthe first selected application comprises a food application and thesecond selected application comprises a hotel application, and whereinenabling the first and second selected applications to perform the oneor more data transfers with the user account based at least on the datasent comprises: enabling the food application to perform a data transferthat generates a food order based at least on the data sent to the foodapplication; and enabling the hotel application to perform a datatransfer that generates a hotel reservation based at least on the datasent to the hotel application.
 9. A non-transitory machine-readablemedium having stored thereon machine-readable instructions executable tocause a machine to perform operations comprising: causing a providerapplication of a mobile device to request an operating system of themobile device to identify one or more other applications of the mobiledevice configured to perform one or more data transfers associated witha user account; in response to the request to the operating system,retrieving application identification data from the operating systemthat identifies a first application au a second application of themobile device configured to perform the one or more data transfersassociated with the user account; in response to retrieving theapplication identification data, causing the provider application todisplay a first icon and a second icon on a graphic user interface thatcorrespond with the first application and the second application,respectively: determining, through the provider application and withoutmanual input, a first set of data types required for the firstapplication to perform. the one or more data transfers associated withthe user account and a second set of data types for the secondapplication to perform the one or more data transfers associated withthe user account, wherein the first set or data types is different fromthe second set of data types; and maintaining, through the providerapplication, data corresponding to the first and second set of datatypes for the first and second applications to perform the one or moredata transfers associated with e user account.
 10. The non-transitorymachine-readable medium of claim 9, wherein the operations furthercomprise: causing the provider application to send, without manualinput, the data corresponding to the first set of data types to thefirst application to enable the first application to perform the one ormore data transfers associated with the user account, wherein the firstapplication is enabled to perform the one or more data transfers basedat least on the data sent from the provider application.
 11. Thenon-transitory machine-readable medium of claim 10, wherein the firstset of data types comprises an e-mail address data type and a passworddata type, wherein the data sent to the first application comprises anemail address and a password associated with the user account, andwherein the first application is enabled to perform the one or more datatransfers associated with the user account based at least on the emailaddress and the password.
 12. The non-transitory machine-readable mediumof claim 9, wherein the operations further comprise: causing theprovider application to display a respective enable button for each ofthe first and second applications on the graphical user interface; andenabling the first and second applications to perform the one or moredata transfers associated with the user account based at least on one ormore inputs received with the respective enable buttons.
 13. Thenon-transitory machine-readable medium of claim 9, wherein theoperations further comprise: causing the provider application to displaya respective toggle button for each of the first and secondapplications, and wherein the first and second applications are enabledto perform the one or more data transfers or disabled from performingthe one or more data transfers based at least on one or more inputsreceived with the respective toggle buttons.
 14. The non-transitorymachine-readable medium of claim 9, wherein the operations furthercomprise: causing the provider application to display icons representingone or more installable applications on the graphical user interface;and causing the provider application to display a respective installbutton for each of the one or more installable applications on thegraphic user interface, and wherein the one or more installableapplications are installed based at least on one or more inputs receivedwith the respective install buttons.
 15. The non-transitorymachine-readable medium of claim 14, wherein the operations furthercomprise: installing a third application from the one or moreinstallable applications based at least on the one or more inputsreceived with the respective install buttons; determining, through theprovider application and without manual input, a third set of data typesrequired for the third application to perform the one or more datatransfers associated with the user account, wherein the third set ofdata types is different from the first set of data types and the secondset of data types; and causing the provider application to transfer datacorresponding to the third set of data types to the third application toenable the third application to perform the one or more data transfersassociated with the user account.
 16. A method, comprising: determininga provider application configured to access a user account associatedwith a provider server; identifying a plurality of other applicationsconfigured to communicate with the provider server; displayingidentifiers representing the plurality of other applications on agraphical user interface of a mobile device; receiving a user selectionof a first application and a second application from the plurality ofother applications displayed; determining, through the providerapplication and without manual input, a first set of data types requiredby the first selected application to perform one or more data transferswith the user account and a second set of data types required for thesecond selected application to perform the one or more data transferswith the user account, wherein the first set of data types is differentfrom the second set of data types; causing the provider application tosend the data corresponding, to the first set of data types to the firstselected application and data corresponding to the second set of datatypes to the second selected application; and enabling the first andsecond selected applications to perform the one or more data transferswith the user account based at least on the data sent to the first andsecond selected applications.
 17. The method of claim 16, furthercomprising: generating an advertisement comprising an incentive based atleast on a purchase made with the first application or the secondapplication; and displaying the advertisement on the mobile device. 18.The method of claim 16, wherein the first set of data types comprises anemail address data type and a password data type, wherein the data sentto the first application includes an email address and a passwordassociated with the user account, and wherein the first application isenabled to perform the one or more data transfers with the user accountbased at least on the email address and the password.
 19. The method ofclaim 16, further comprising: retrieving application identification datathat identifies the plurality of other applications of the mobiledevice, wherein the application identification data indicates one ormore installable applications configured to perform the one or more datatransfers with the provider; and displaying a respective install buttonfor each of one or more installable applications on the graphical userinterface of the mobile device, and wherein the one or more installableapplications are configured to be installed based at least on one ormore inputs received with the respective install buttons.
 20. The methodof claim 19, further comprising: installing a third application from theone or more installable applications based at least on the one or moreinputs received with the respective install buttons; determining,through the provider application and without manual input, a third setof data types required for the third application to perform the one ormore data transfers with the user account, wherein the third set of datatypes is different from the first and second sets of data types; andcausing the provider application to send data corresponding to the thirdset of data types to the installed application to enable the thirdapplication to perform the one or more data transfers with the useraccount.